The token name was misused: Sometimes it was assumed to be a symbol and sometimes an ID. This caused issues now that we use token IDs that are different from the symbols. (also, the name had nothing to do with the ERC20 name..)

Token name has therefore been replaced by id and symbol in all relevant places. Configuration files have been converted to use the token instance ID's from the context-addresses package to avoid ambiguity among (1) different tokens with the same symbol and (2) multiple token instances such as USDC (Circle issued) and USDC.e (bridged from Ethereum).

Default token IDs can be registered for a symbol and network. And if there is only one ID for a given symbol on a network, it will be considered the default. Mangrove.token() will create an instance of the default token ID if found.

In addition, the following changes have been made:

• MgvToken has been renamed to Token. The prefix was at best confusing.
• The Mangrove.openMarkets function now returns Tokens instead of a bespoke token data struct.
• Mangrove.market and Market.connect now accept either symbol, token ID, or Token for base and quote.
• {Mangrove, Token}.getTokenAddress(symbolOrId) function has been added.
• Added displayName and displayedAsPriceDecimals to Token.
• Token data is now always retrieved through the configuration and thus stored/cached in one place. A number of functions used to ignore the configuration and one even used a separate cache based on the moize package..
• Throw error in Token.getDecimals if decimals are not on record.

Some unnecessary/redundant code/features have been removed as it simplified the task and made the code shorter and clearer:

• Removed configuration.tokens.fetchDecimalsFromAddress. Instead, use Token.createTokenFromAddress and read the decimals from that token.
• Removed Mangrove.getTokenAndAddress. Instead, use Mangrove.tokenFromAddress and read the address from there.
• Removed Mangrove.tokenFromConfig. Use Mangrove.token instead.
• Removed Mangrove.getNameFromAddress: It was ambiguous (multiple names could be registered) and only used for resolving tokens which can now be done with the new configuration.tokens.getTokenIdFromAddress() function.
• Removed token configuration getters and setters from Mangrove and Token. Instead, use the methods on configuration.tokens.
• Mangrove.toUnits|fromUnits no longer accepts a token name/symbol as this was ambiguous. Instead, use Token.createToken and call toUnits|fromUnits on that.